test_runner: show interrupted test on SIGINT #61676
Open
+100
−4
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Collaborator
|
Review requested:
|
nodejs-github-bot
added
needs-ci
When the test runner process is killed with SIGINT (Ctrl+C), display which test was running at the time of interruption. This makes it easier to identify tests that hang or take too long. - Add `test:interrupted` event emitted when SIGINT is received - Add `interrupted()` method to TestsStream - Handle the event in both TAP and spec reporters - TAP outputs: `# Interrupted while running: <test>` - Spec outputs with yellow header and warning symbol - Use setImmediate to allow reporter stream to flush before exit With process isolation (default), shows the file path since the parent runner only knows about file-level tests. With --test-isolation=none, shows the actual test name.
mcollina
force-pushed
the
test-runner-show-interrupted-test
branch
from
dbbd948 to
ad00a26
Compare
Member
JakobJingleheimer
left a comment
JakobJingleheimer
left a comment
There was a problem hiding this comment.
Sounds like a good idea/feature, and the initial implementation LGTM 🙂
MoLow
approved these changes
Feb 8, 2026
mcollina
added
request-ci
github-actions
bot
removed
the
request-ci
Collaborator
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## main #61676 +/- ##
==========================================
- Coverage 89.74% 89.72% -0.03%
==========================================
Files 674 675 +1
Lines 204360 204592 +232
Branches 39265 39303 +38
==========================================
+ Hits 183412 183560 +148
- Misses 13251 13307 +56
- Partials 7697 7725 +28
🚀 New features to boost your workflow:
|
aduh95
reviewed
Feb 8, 2026
| defined. | ||
| The corresponding execution ordered event is `'test:complete'`. | ||
|
|
||
| ### Event: `'test:interrupted'` |
Contributor
There was a problem hiding this comment.
Suggested change
| ### Event: `'test:interrupted'` | |
| ### Event: `'test:interrupted'` | |
| <!-- YAML | |
| added: REPLACEME | |
| --> |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
When the test runner process is killed with SIGINT (Ctrl+C), display which test was running at the time of interruption. This makes it easier to identify tests that hang or take too long.
Changes
test:interruptedevent emitted when SIGINT is receivedinterrupted()method to TestsStream# Interrupted while running: <test>Behavior
--test-isolation=none: shows the actual test name and locationExample output (TAP)
Example output (spec)